core: Add API (and standard concept for) content checksum
authorColin Walters <walters@verbum.org>
Thu, 8 Feb 2018 21:33:18 +0000 (16:33 -0500)
committerAtomic Bot <atomic-devel@projectatomic.io>
Mon, 12 Feb 2018 19:03:18 +0000 (19:03 +0000)
commit0041a7a1ed8173a6497429520ed06e981703625c
tree65343912a72d807468c0c6fe20d7a2d6cba1093c
parent5848de93a4346ad3c49d907ced7612578781f5e8
core: Add API (and standard concept for) content checksum

There are a few cases for knowing whether a commit has identical
content to another commit.  Some people want to do a "promotion workflow",
where the content of a commit on a tesitng branch is then "promoted"
to a production branch with `ostree commit --tree=ref`.

Another use case I just hit in rpm-ostree deals with
[jigdo](https://github.com/projectatomic/rpm-ostree/issues/1081) where we're
importing RPMs on both the client and server, and will be using the
content checksum, since the client/server cases inject different metadata
into the commit object.

Closes: https://github.com/ostreedev/ostree/issues/1315
Closes: #1449
Approved by: jlebon
apidoc/ostree-sections.txt
src/libostree/libostree-devel.sym
src/libostree/ostree-core.c
src/libostree/ostree-core.h
src/ostree/ot-dump.c
tests/basic-test.sh